@wesblake Hello,
Using the information you've provided I've managed to upload my package to the appstore using Transporter, however even after inserting com.apple.application-identifier and com.apple.developer.team-identifier to my .entitlements file, I still get "Not Available for Testing" status in TestFlight.

Could you share any other entries in the entitlements file, or any other leads to resolve this issue?

If you mean that macdeployqt still gives you the same error, then that's normal. We run it before modifying these libraries.

If you want macdeployqt to not scream at these libraries, you can change the original files and put the whole path to them with -change.

Thanks for your help ! I will take a look a that, and post another thread if I have a lot of problems.

I updated a .pro file to the following state:

QT += core multimedia widgets
QT -= gui
TARGET = MetadataExtractor
CONFIG += console
CONFIG += static
TEMPLATE = app
SOURCES += main.cpp
extractor.cpp
HEADERS +=
extractor.h

Then used the macdeployqt. This issue is resolved for me.
@SGaist @Tyras @kshegunov Thanks to Everyone!

QtWebChannel is the way to go for that kind of stuff with QtWebEngine

Hi,

You could try with an eventFilter and handle QEvent::InputMethod in there

Hope it helps

@SGaist thanks for reply) I understand that I need that for deployment on device but I am building just qt not an app. So i thought it might be unnecessary for building Qt itself. Cause when i am downloading qt for Ios i don't need to have that account. But i need it to build qt that's strange for me. I have ready code to port to ios so openssl is needed

No problem :)

Since you have it working now, please update the thread title prepending [solved] so other forum users may know that a solution has been found :)

Also, when encountering answer(s) that helped you, please consider up-voting them so that other users may find them more easily.

Happy coding !